2015-04-14 - 16728 - SNC Approach on Single Work Order Create for a PO #ProductionBreakFix #SNCProject #sncsup #ABAPSNC

2015-04-14 - 16728 - Approach Doc - SNC Create Single Work per PO


Problem Summary


Currently Work Orders (WOs) are created at Purchase Order item level. This creates user and system issues that need to be addressed:
  1. High number of user confirmations required- If there are many lines in the PO, multiple WOs are created one per a PO Line.For example, : If a PO has 500 lines system creates 500 work orders then the user has to click 500 items for each phase of a WO.
  2. Confirmation Idocs fail and have to be manually reprocessed.

Admin Info

Purpose
 SNC Create single Work Order per PO
Requested by
 Jeffery Mau
Issue Date
 04-14-2015
Resolved by
 Adithya, Venkat
Document Status
 Complete

Estimates

Option 1 Estimates:
Sl.No
 Activity
 Estimation in Hours
1
 Research
2
 Documentation
3
 Development/ Config
 120
4
 Unit test in DEV
 40
5
 Unit test in QUA
6
 Other activity

TOTAL
 160

Summary Solution

New Era would like to create a single work order (with 4 reporting phases) for the PO. Any statuses confirmed on this item would be updated on all other items of the ECC PO via a program. Unfortunately a single WO cannot be created at the header level. Therefore such a single WO would need to be created line level. There are three options for line level WOs:

Option 1: Users will confirm status on only one Active Item of the PO.
Option 2: Create a dummy WO reporting material in Line 9999 Item of the ECC PO.
Option 3: WO list screen will be enhanced to allow selecting multiple status checkboxes.

Option 1: Users will confirm status on only one Active Item of the PO.
- The current WO list program will be modified to create only one worklist for the first active item
- Statuses reported on this WO will be presumed to be for the ENTIRE PO.
- If the first active item is subsequently deleted in ECC, another Worklist will be generated for reporting.

Design highlights
Programs Impacted
1) CHANGED: SNC- WO List Program - Single WO list should be created with Item First Active Item - SNC
2) NEW: ECC- Develop a program to update all Lines of PO if item First Active Item is confirmed - ECC

Exception case if required


NEW: SNC - Develop a program to Close/Delete WO for cancelled Item (provided status not reported yet)
This may not be required if the Critical Step PO Publish is done after all the negotiations are completed and no changes are done to PO after this milestone.

Validation required:
- Validate statuses and data in SNC POs are same as in current production across all Order Types
- Validate SNC ASNs function the same as in current production and Shipping and Booking data sent to Freight Forwarder are unchanged

Option 2: Create a dummy WO reporting material in Line 9999 Item of the ECC PO
- Line 9999 will have to be added automatically to all new SNC POs in ECC
- This dummy line will be transmitted to SNC.
- The current WO create program will be modified to create only one WO for the this line 9999
- Phase Master data for future new materials will not be required
- Line 9999 will need to be removed from all non-SNC data - e.g. Freight Forwarder files, Inbound deliveries, Customer ASNs, PO feeds, idocs to Menlo, PO forms, etc.

Programs Impacted
1) NEW: ECC-Develop a program to add Item 9999 to SNC PO's
2) CHANGED: SNC- WO Create Program - Single WO should be created with Item 9999
3) NEW: ECC-Develop Program to update all Lines of PO if item 9999 is confirmed - ECC
4) CHANGED: ECC- Inbound delivery should not be created for line 9999

Validation required:
- PO Forms - Do we need to suppress 9999?
- PO Feed Extract in SNC and ECC - Do we need to suppress 9999?
- DLF PO Program - Do we need to suppress 9999?
- Total cost and quantity on a PO?
- MIGO/PGI - How to Ignore 9999? - Maybe Text Material will resolve some of these issues?
- Will ASN allow publish in SNC for all lines of PO?
- Are all lines are extracted in file or just one line is sent Freight Forwarder?

Option 3: WO list screen will be enhanced to allow selecting multiple status checkboxes.
This requires investigation of the technical code for feasibility

Solution Analysis and Recommendations

(Include Screen Shots if required)

Option 2 was rejected because having wide Impact on several Objects of the SNC & ECC.
Option 3 was investigated but rejected because it would not address the multiple I DOC issue also being investigated in parallel

Resolution

Option 1 will be developed.